Digital document repository access control using encoded graphical codes

ABSTRACT

A device configured to obtain a first graphical code that represents a public encryption key for an organization and to extract the public encryption key for the organization from the first graphical code. The device is further configured to obtain a second graphical code that represents a digital document comprising data and a digital signature that was signed using a private encryption key for the organization. The device is further configured to extract the digital document from the second graphical code and to validate the second graphical code using the public encryption key for the organization. The device is further configured to determine the second graphical code passes validation using the public encryption key for the organization and to store the digital document in a digital document repository.

TECHNICAL FIELD

The present disclosure relates generally to information security, andmore specifically to digital document repository access control usingencoded graphical codes.

BACKGROUND

In a network environment, devices are in data communication with otherdevices that may be distributed anywhere in the world. These networkenvironments allow data and information to be shared among devices. Someof the technical challenges that occur when data is exchanged betweendevices are controlling data leakage, unauthorized access to data, andpreventing malicious activities. Data storing devices, such as userdevices, databases, and servers, are vulnerable to attacks. Thisvulnerability poses several network security challenges. Existingsystems are typically unable to detect a network attack until after theattack has occurred. For example, a bad actor may store malicious filesor documents in a memory which then allows the bad actor to gainunauthorized access to other files or documents that are also stored inthe memory. Having a delayed response allows the bad actor to gainaccess to sensitive information within the network and/or allows badactors to perform other malicious activities such as data exfiltrationor uploading malware.

SUMMARY

The disclosed system provides several practical applications andtechnical advantages that overcome the previously discussed technicalproblems. For example, the disclosed system provides a practicalapplication by providing a process that allows a device to validatedigital documents using encoded graphical codes before storing thedigital documents in memory. This process generally involves extractinga public encryption key that is encoded in a graphical code and thenusing the public encryption key to validate a digital signature that isembedded within a digital document. The digital document itself is alsoencoded as a different graphical code. This process improves informationsecurity by allowing the device to validate the digital signature ofdigital documents before the digital documents are stored in memory.This process provides a technical advantage by enabling the device toreject digital documents that do not successfully pass validation whichhelps to prevent malicious documents from being stored in memory. Thisalso provides the technical advantage of obfuscating the data within adigital document by using an encoded graphical code. This processprevents other people (e.g. bad actors) from being able to read oraccess the data within the digital document until the digital documenthas been decoded and stored in memory.

Improving information security for the system also improves theunderlying network and the devices within the network. For example, whena data exfiltration attack occurs, there is an increase in the number ofnetwork resources and bandwidth that are consumed which reduces thethroughput of the network. By preventing data exfiltration attacks, thesystem is able to prevent any unnecessary increases in the number ofnetwork resources and bandwidth that are consumed that would otherwisenegatively impact the throughput of the system. As another example, whena malware attack occurs, one or more devices may be taken out of serviceuntil the malware can be removed from the devices. Taking devices out ofservice negatively impacts the performance and throughput of the networkbecause the network has fewer resources for processing and communicatingdata. By preventing malware types of attacks, the system prevents anycomprised devices from being taken out of service due to an attack thatwould otherwise negatively impact the performance and throughput of thenetwork.

In one embodiment, the information system comprises a device that isconfigured to obtain a first graphical code that represents a publicencryption key for an organization and to extract the public encryptionkey for the organization from the first graphical code. The device isfurther configured to obtain a second graphical code that represents adigital document that comprises data and a collision mitigating versionof the data (e.g. a hash) that was signed using a private encryption keyfor the organization. The device is further configured to extract thedigital document from the second graphical code and to validate thesecond graphical code using the public encryption key for theorganization. The device is further configured to determine the secondgraphical code passes validation using the public encryption key for theorganization and to store the digital document in a digital documentrepository.

In another embodiment, the information system comprises a device that isconfigured to identify a first digital document in a digital documentrepository, to identify a first graphical code that represents the firstdigital document, and to send the first graphical code to an approveduser device. The device is further configured to obtain a secondgraphical code that represents a public encryption key for theorganization and to extract the public encryption key for anorganization from the second graphical code. The device is furtherconfigured to obtain a third graphical code from the approved userdevice. The third graphical code represents a second digital documentthat comprises data and a collision mitigating version of the data thatwas signed using a private encryption key for the organization. Thedevice is further configured to determine the third graphical codepasses validation using the public encryption key for the organizationand to store the second digital document in a digital documentrepository.

Certain embodiments of the present disclosure may include some, all, ornone of these advantages. These advantages and other features will bemore clearly understood from the following detailed description taken inconjunction with the accompanying drawings and claims.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of this disclosure, reference is nowmade to the following brief description, taken in connection with theaccompanying drawings and detailed description, wherein like referencenumerals represent like parts.

FIG. 1 is a schematic diagram of an embodiment of an information systemthat is configured to employ a digital document repository;

FIG. 2 is a flowchart of an embodiment of a digital document storingprocess for the information system;

FIG. 3 is a flowchart of an embodiment of a digital document updatingprocess for the information system; and

FIG. 4 is an embodiment of a device configured with a digital documentrepository.

DETAILED DESCRIPTION

System Overview

FIG. 1 is a schematic diagram of an embodiment of an information system100 that is configured to employ a digital document repository 120. Theinformation system 100 is generally configured to encode information andto validate digital documents 122 using encoded graphical codes. Thisprocess generally involves a user device 102 obtaining a first graphicalcode (e.g. a first Quick Response (QR) code) that is encoded with apublic encryption key 112 and extracting the public encryption key 112from the first graphical code. The user device 102 then obtains adigital document 122 that is encoded using a second graphical code (e.g.a second QR code) that is different from the first graphical code. Thedigital document 122 comprises data 124 and a digital signature 126 thatwas signed using a private encryption key 114. The digital signature 126comprises a collision mitigating version of the data 124, for example, ahash. The user device 102 uses the previously extracted publicencryption key 112 to validate the digital signature 126 of the digitaldocument 122. The user device 102 may then store the digital document122 in a digital document repository 120 after determining that thedigital signature 126 of the digital document 122 passes validation.This process provides information security for the digital documentrepository 120 by only storing digital documents 122 that are associatedwith valid digital signatures 126. This process prevents potentiallymalicious digital documents 122 from being stored within the digitaldocument repository 120.

In one embodiment, the information system 100 comprises one or more userdevices 102, a kiosk 104, and a database 108 that are in signalcommunication with each other over a network 110. The network 110 may beany suitable type of wireless and/or wired network including, but notlimited to, all or a portion of the Internet, an Intranet, a privatenetwork, a public network, a peer-to-peer network, the public switchedtelephone network, a cellular network, a local area network (LAN), ametropolitan area network (MAN), a personal area network (PAN), a widearea network (WAN), a Bluetooth network, a WiFi network, a Near FieldCommunication (NFC) network, and a satellite network. The network 110may be configured to support any suitable type of communication protocolas would be appreciated by one of ordinary skill in the art.

Kiosk

A kiosk 104 is a device that is located in a space 105 is associatedwith an organization or a business that provides services or products tousers. Examples of the kiosk 104 include, but are not limited to, acomputer, tablet, a point-of-sale device, a card reader, or any othersuitable type of device. For example, the kiosk 104 may be a device in astore where a user is shopping. As another example, the kiosk 104 may bedevice in a location where a user can rent items or supplies. A publicencryption key 112 and a private encryption key 114 are both assigned tothe organization. The private encryption key 114 is a string of numericvalues (e.g. hexadecimal values or binary values) that are used forencrypting data and generating a digital signature 126. The publicencryption key 112 is a string of numeric values that are used fordecrypting data and validating digital signatures that are signed usingthe private encryption key 114. The private encryption key 114 and thepublic encryption key 112 may be any suitable type of key that can beused for encrypting and decrypting data. The public encryption key 112can be encoded into a graphical code. Examples of a graphical codeinclude, but are not limited to, a barcode, a two-dimensional barcode(e.g. QR code), a symbol, or any other suitable type of encodedgraphical representation. The graphical code for the public encryptionkey 112 is readily available and is sharable with the public. Forexample, the graphical code for the public encryption key 112 may bedisplayed on the kiosk 104 or at the space 105 where the kiosk 104 ispresent, for example, within a store.

User Devices

Examples of user devices 102 include, but are not limited to, asmartphone, a tablet, a laptop, a computer, a smart device, anInternet-of-Things (IoT) device, or any other suitable type of device.In one embodiment, a user device 102 comprises a document managementengine 116 and a memory 118. Additional details about the hardwareconfiguration of the user device 102 are described in FIG. 4 . Thememory 118 is configured to store a digital document repository 120,digital documents 122, data 124, digital signatures 126, publicencryption keys 112 for organizations, and/or any other suitable type ofdata.

In one embodiment, the document management engine 116 is generallyconfigured to use graphical codes to store digital documents 122 in thedigital document repository 120. The digital document repository 120 isa portion of the memory that is allocated to securely storing digitaldocuments 122. For example, the digital document repository 120 may beaccessible using an application on the user device 102 after providingauthentication credentials for a user. Examples of authenticationcredentials include, but are not limited to, a username and password, asecurity code, a token code, a personal identification number (PIN), afingerprint, biometric information, or any other suitable type orcombination of user input that can be used to authenticate a user.

In one embodiment, a digital document 122 comprises data 124 and adigital signature 126. Examples of data 124 include, but are not limitedto, text, images, documents, files, video files, audio files, or anyother suitable type of data. As an example, the data 124 may be adocument that identifies a purchase of one or more items from anorganization. In this example, the data 124 may be a document thatidentifies one or more items, a timestamp, transaction information,and/or any other suitable type of information associated with thepurchase. As another example, the data 124 may be a document thatcomprises a warranty, guarantee, or contract that is associated with anorganization. In this example, the data 124 may be a document thatidentifies one or more items, a timestamp, terms of conditions, and/orany other suitable type of information. The digital signature 126 is asecurity feature that is provided by an organization to verify theauthenticity of a digital document 122 and its data 124. In oneembodiment, the digital signature 126 may be generated by performing ahashing operation on the data 124 to generate a hash value and thenencrypting the hash value using a private encryption key 114 to generatethe digital signature 126. In other embodiments, the digital signature126 may be generated using any other suitable technique.

Databases

Examples of a database 108 include, but are not limited to, filerepositories, computers, databases, memories, servers, shared folders,or any other suitable type of networking device. The database 108 isgenerally configured to store digital documents 122 and/or any othersuitable type of information that is associated with the informationsystem 100. In FIG. 1 , the information system 100 shows a singledatabase 108. In other embodiments, the information system 100 maycomprise any other suitable number of databases 108.

Digital Document Storing Process

FIG. 2 is a flowchart of an embodiment of a digital document storingprocess 200 for the information system 100. The information system 100may employ process 200 to securely store digital documents 122 within adigital document repository 120 after the digital documents 122 passvalidation using encoded graphical codes. This process providesinformation security for the digital document repository 120 by onlystoring digital documents 122 that are associated with valid digitalsignatures 126.

At step 202, the user device 102 obtains a first graphical code 128 thatrepresents a public encryption key 112 for an organization. As anexample, the first graphical code 128 may be a QR code that is displayedat a location (e.g. a store) where a kiosk 104 is present. In thisexample, a user may capture an image of the first graphical code 128using a camera 406 on the user device 102. As another example, the firstgraphical code 128 may be a QR code that is displayed online on a webpage that is associated with the organization. In this example, the usermay download an image of the first graphical code 128 onto their userdevice 102. In other examples, the user may use any other suitabletechnique to copy an image of the first graphical code 128 onto the userdevice 102. After obtaining the first graphical code 128, the userdevice 102 decodes the first graphical code 128 to extract the publicencryption key 112 from the first graphical code 128. For example, theuser device 102 may input the first graphical code 128 into a QR codereader to read the first graphical code 128 and to extract the publicencryption key 112 from the first graphical code 128. In other examples,the user device 102 may employ image processing or any other suitabletechnique to decode and extract the public encryption key 112 from thefirst graphical code 128. In some embodiments, the user device 102 mayvalidate the public encryption key 112 using a key (e.g. a publicencryption key) from an external certification authority. This processallows the user device 102 to confirm that the public encryption key 112is valid and comes from a trusted or reputable source.

At step 204, the user device 102 obtains a second graphical code 130that represents a digital document 122 that was signed using a privateencryption key 114 for the organization. As an example, the digitaldocument 122 may comprise data 124 that corresponds with a receipt or awarranty for one or more items that a user obtains or purchases from theorganization. In other examples, the digital document 122 may includeany other suitable type of data 124. The kiosk 104 then generates adigital signature 126 that will be included in the digital document 122.For instance, the kiosk 104 may perform a hashing operation on the data124 to generate a hash value and then encrypt the hash value with theprivate encryption key 114 for the organization to generate the digitalsignature 126. In other embodiments, the kiosk 104 may generate thedigital signature 126 using any other suitable technique. Aftergenerating the digital signature 126, the kiosk 104 converts the data124 and the digital signature 126 into the second graphical code 130(e.g. a QR code) by encoding the data 124 and the digital signature 126.The kiosk 104 may use any suitable type of encoding technique to convertthe digital document 122 into the second graphical code 130. In someembodiments, the kiosk 104 may generate more than one graphical codewhen the size of data 124 exceeds the size limit of data that can berepresented using a single graphical code.

After generating the second graphical code 130, the kiosk 104 outputsthe second graphical code 130 to the user device 102. The kiosk 104 mayemploy any suitable technique for outputting the second graphical code130 to the user device 102. For example, the kiosk 104 may display thesecond graphical code 130 on a graphical user interface (e.g. a display)of the kiosk 104. In this example, the user device 102 may capture animage of the second graphical code 130 to obtain the second graphicalcode 130. As another example, the kiosk 104 may print out the secondgraphical code 130 onto a physical document. In this example, the userdevice 102 may capture an image of the second graphical code 130 on thephysical document to obtain the second graphical code 130. As anotherexample, the kiosk 104 may send a message or an email that includes thesecond graphical code 130 to the user device 102. In this example, theuser device 102 may download an image of the second graphical code 130from the message or email to obtain the second graphical code 130.

After obtaining the second graphical code 130, the user device 102 willprocess the second graphical code 130 to determine whether the secondgraphical code 130 corresponds with a valid digital document 122 basedon digital signature 126 of the digital document 122. At step 206, theuser device 102 extracts the digital document 122 from the secondgraphical code 130. In one embodiment, the user device 102 may input thesecond graphical code 130 into a QR code reader to read the secondgraphical code 130 and to extract the data 124 and the digital signature126 of the digital document 122 from the second graphical code 130.Through this process, the user device 102 converts the second graphicalcode 130 back into the original format of the data 124. For example, theuser device 102 may convert the second graphical code 130 into text,images, documents, files, or any other suitable type of data format. Inother examples, the user device 102 may employ image processing or anyother suitable technique to extract the data 124 and the digitalsignature 126 from the second graphical code 130.

At step 208, the user device 102 determines whether the second graphicalcode 130 is valid. After extracting the data 124 and the digitalsignature 126 from the second graphical code 130, the user device 102performs a hashing operation on the data 124 to generate a first hash.The user device 102 then decrypts the digital signature 126 using thepublic encryption key 112 for the organization to recover a second hash.The user device 102 then compares the first hash to the second hash todetermine whether the digital signature 126 and the second graphicalcode 130 are valid. The user device 102 determines that the secondgraphical code 130 is valid when the first hash matches the second hash.Otherwise, the user device 102 determines that the second graphical code130 is invalid when the first hash does not match this second hash. Inother embodiments, the user device 102 may employ any other suitabletechnique for validating the second graphical code 130.

The user device 102 terminates process 200 in response to determiningthat the second graphical code 130 is invalid. In this case, the userdevice 102 will not store the digital document 122 in the digitaldocument repository 120 since the second graphical code 130 failsvalidation. This process provides information security for the digitaldocument repository 120 by only storing digital documents 122 that areassociated with valid digital signatures 126. The user device 102proceeds to step 210 in response to determining that the secondgraphical code 130 is valid. In this case, the user device 102 proceedsto step 210 to store the digital document 122 in the digital documentrepository 120.

At step 210, the user device 102 stores the digital document 122 in thedigital document repository 120. Here, the user device 102 may store thedigital document 122, the data 124, the digital signature 126, and/orthe second graphical code 130. In some embodiments, the user device 102may be further configured to store a copy of the digital document 122,the data 124, the digital signature 126, and/or the second graphicalcode 130 in a remote database 108. For example, the user device 102 maygenerate a copy of the digital document 122 and send the copy of thedigital document 122 to the remote database 108. This process allows theuser device 102 to store copies of the digital document 122 that can beaccessed or downloaded by other devices. For example, this processallows a user to access and view their digital documents 122 usinganother user device 102.

Digital Document Updating Process

FIG. 3 is a flowchart of an embodiment of a digital document updatingprocess 300 for the information system 100. The information system 100may employ process 300 to authorize other people to perform actions onbehalf of the user using the digital document 122 that are stored in theuser's digital document repository 120. Process 300 allows the user toshare a digital document 122 as an encoded graphical code which allowsthe authorized person to use the digital document 122 on behalf of theuser. After the authorized person has completed some action using thedigital document 122, the digital document 122 is then updated andreturned back to the user for storing in their digital documentrepository 120. This process allows the user device 102 to store theupdated digital documents 122 within a digital document repository 120after the updated digital documents 122 pass validation using graphicalcodes.

As an example, a user may want to send a digital document 122 to anotherperson to authorize the person to perform actions on behalf of the userusing the digital document 122. For example, the user may authorize theperson to return or exchange one or more items that are identified on adigital document 122. As another example, the user may authorize theperson to initiate a warranty claim using the digital document 122. Inother examples, the user may authorize the person to perform any othersuitable type of action using the digital document 122. At step 302, theuser device 102 identifies a digital document 122 in the digitaldocument repository 120. The user may identify a digital document 122 byaccessing the digital documents 122 in the digital document repository120 and then selecting (e.g. clicking) the digital document 122 fromamong the digital documents 122 in the digital document repository 120.In other examples, the user may use any other suitable technique toidentify a digital document 122 within the digital document repository120.

At step 304, the user device 102 identifies a first graphical code 132that represents the digital document 122. In one embodiment, the userdevice 102 identifies a first graphical code 132 (e.g. a QR code) thatwas previously stored and associated with the identified digitaldocument 122. In another embodiment, the user device 102 may create orrecreate the first graphical code 132. For example, the user device 102may convert the digital document 122 into the first graphical code 132by encoding text from the digital document 122 into a QR code. The userdevice 102 may use any suitable technique for converting the digitaldocument 122 into the first graphical code 132.

At step 306, the user device 102 sends the first graphical code 132 toan approved user device 102A. The user device 102 begins by identifyinganother user device 102A that will be used by the person that isauthorized to perform actions using the digital document 122 on behalfof the user. The user device 102 may identify the approved user device102A using a device name, a phone number, an email address, an MediaAccess Control (MAC) address, an Internet Protocol (IP) address, or anyother suitable identifier that identifies the approved user device 102A.After identifying the approved user device 102A, the user device 102 mayuse any suitable messaging technique to send the first graphical code132 to the approved user device 102A. For example, the user device 102may send the first graphical code 132 to the approved user device 102Aas a media message or an email. As another example, the user device 102may send the first graphical code 132 to the approved user device 102Ausing over a Bluetooth connection, a WiFi connection, an NFC connection,an RFID connection, or any other suitable type of connection.

At step 308, the user device 102 obtains a second graphical code 134that represents a public encryption key 112 for an organization. In oneembodiment, the user device 102 may receive the second graphical code134 (e.g. a QR code) from the approved user device 102A. For example,the approved user device 102A may send the second graphical code 134 tothe user device 102 as a message. In this example, the approved userdevice 102A may use any suitable messaging technique to send the secondgraphical code 134 to the user device 102. In some embodiments, the userdevice 102 may obtain the second graphical code 134 from memory 118 orthe digital document repository 120. For example, the user device 102may have previously stored the second graphical code 134 in memory whenthe digital document 122 was stored. In some embodiments, the secondgraphical code 134 may be displayed online on a web page that isassociated with the organization. In this example, a user may downloadan image of the second graphical code 134 onto the user device 102.

At step 310, the user device 102 receives a third graphical code 136that represents an updated digital document 122 that was signed using aprivate encryption key 114 for the organization. The updated digitaldocument 122 includes data 124 that has been revised or updated after auser of the approved user device 102A performs some action using thedigital document 122. As an example, the user of the approved userdevice 102A may return or exchange one or more items that are identifiedon the digital document 122. As another example, the user of theapproved user device 102A may initiate a warranty claim using thedigital document 122. In other examples, the user of the approved userdevice 102A may perform any other suitable type of action using thedigital document 122.

After the user performs an action using the digital document 122, thekiosk 104 may update the data 124 within digital document 122 andgenerate a new digital signature 126 for the digital document 122. As anexample, the kiosk 104 may perform a hashing operation on the updateddata 124 to generate a hash value and then encrypt the hash value withthe private encryption key 114 for the organization to generate a newdigital signature 126. In other embodiments, the kiosk 104 may generatethe new digital signature 126 using any other suitable technique. Aftergenerating the new digital signature 126, the kiosk 104 may then encodethe updated data 124 and the new digital signature 126 as the thirdgraphical code 136 (e.g. a QR code). The kiosk 104 may use any suitabletype of encoding technique to convert the digital document 122 into thethird graphical code 136. This process allows the kiosk 104 to generatean updated digital document 122 that is a modified version of theoriginal digital document 122.

After generating the third graphical code 136, the kiosk 104 outputs thethird graphical code 136 to the approved user device 102A. The kiosk 104may employ any suitable technique for outputting the third graphicalcode 136 to the approved user device 102A. For example, the kiosk 104may display the third graphical code 136 on a graphical user interface(e.g. a display) of the kiosk 104. In this example, the approved userdevice 102A may capture an image of the third graphical code 136 toobtain the third graphical code 136. As another example, the kiosk 104may print out the third graphical code 136 onto a physical medium ordocument. In this example, the approved user device 102A may capture animage of the third graphical code 136 on the physical document to obtainthe third graphical code 136. As another example, the kiosk 104 may senda message or an email that includes the third graphical code 136 to theapproved user device 102A. In this example, the approved user device102A may download an image of the third graphical code 136 from themessage or email to obtain the third graphical code 136.

After the approved user device 102A obtains the third graphical code136, the approved user device 102A sends the third graphical code 136back to the user device 102. In this example, the approved user device102A may use any suitable messaging technique to send the thirdgraphical code 136 to the user device 102. For example, the approveduser device 102A may send the third graphical code 136 to the userdevice 102 as a media message or an email. As another example, theapproved user device 102A may send the third graphical code 136 to theuser device 102 using over a Bluetooth connection, a WiFi connection, anNFC connection, an RFID connection, or any other suitable type ofconnection.

At step 312, the user device 102 extracts the updated digital document122 from the third graphical code 136. In one embodiment, the userdevice 102 may input the third graphical code 136 into a QR code readerto read the third graphical code 136 and to extract the data 124 and thedigital signature 126 of the digital document 122 from the thirdgraphical code 136. Through this process, the user device 102 convertsthe third graphical code 136 back into the original format of the data124. For example, the user device 102 may convert the third graphicalcode 136 into text, images, documents, files, or any other suitable typeof data format. In other examples, the user device 102 may employ imageprocessing or any other suitable technique to extract the data 124 andthe digital signature 126 from the third graphical code 136.

At step 314, the user device 102 determines whether the third graphicalcode 136 is valid. After extracting the data 124 and the digitalsignature 126 from the third graphical code 136, the user device 102performs a hashing operation on the data 124 to generate a first hash.The user device 102 then decrypts the digital signature 126 using thepublic encryption key 112 for the organization to recover a second hash.The user device 102 then compares the first hash to the second hash todetermine whether the digital signature 126 and the third graphical code136 are valid. The user device 102 determines that the third graphicalcode 136 is valid when the first hash matches the second hash.Otherwise, the user device 102 determines that the third graphical code136 is invalid when the first hash does not match this second hash. Inother embodiments, the user device 102 may employ any other suitabletechnique for validating the third graphical code 136.

The user device 102 terminates process 300 in response to determiningthat the third graphical code 136 is not valid. In this case, the userdevice 102 will not store the updated digital document 122 in thedigital document repository 120 since the third graphical code 136 failsvalidation. This process provides information security for the digitaldocument repository 120 by only storing digital documents 122 that areassociated with valid digital signatures 126. The user device 102proceeds to step 316 in response to determining that the third graphicalcode 136 is valid. In this case, the user device 102 proceeds to step316 to store the updated digital document 122 in the digital documentrepository 120.

At step 316, the user device 102 stores the updated digital document 122in the digital document repository 120. Here, the user device 102 maystore the updated digital document 122, the data 124, the digitalsignature 126, and/or the third graphical code 136. In some embodiments,the user device 102 may be further configured to store a copy of thedigital document 122, the data 124, the digital signature 126, and/orthe third graphical code 136 in a remote database 108. For example, theuser device 102 may generate a copy of the updated digital document 122and send the copy of the updated digital document 122 to the remotedatabase 108.

In some embodiments, the approved user device 102A may be configured tovalidate the updated digital document 122 before sending the updateddigital document 122 to the user device 102. For example, the approveduser device 102A may be configured to employ a process similar toprocess 200 that is described in FIG. 2 to validate the updated digitaldocument 122. For redundancy and additional information security, theuser device 102 may also validate the updated digital document 122 afterthe approved user device 102A validates the updated digital document122.

Hardware Configuration for the User Device

FIG. 4 is an embodiment of a user device 102 for the information system100. As an example, the user device 102 may be a smartphone or acomputer. The user device 102 comprises a processor 402, a memory 118, anetwork interface 404, and a camera 406. The user device 102 may beconfigured as shown or in any other suitable configuration.

Processor

The processor 402 comprises one or more processors operably coupled tothe memory 118. The processor 402 is any electronic circuitry including,but not limited to, state machines, one or more central processing unit(CPU) chips, logic units, cores (e.g. a multi-core processor),field-programmable gate array (FPGAs), application-specific integratedcircuits (ASICs), or digital signal processors (DSPs). The processor 402may be a programmable logic device, a microcontroller, a microprocessor,or any suitable combination of the preceding. The processor 402 iscommunicatively coupled to and in signal communication with the memory118, the network interface 404, and the camera 406. The one or moreprocessors are configured to process data and may be implemented inhardware or software. For example, the processor 402 may be 8-bit,16-bit, 32-bit, 64-bit, or of any other suitable architecture. Theprocessor 402 may include an arithmetic logic unit (ALU) for performingarithmetic and logic operations, processor registers that supplyoperands to the ALU and store the results of ALU operations, and acontrol unit that fetches instructions from memory and executes them bydirecting the coordinated operations of the ALU, registers and othercomponents.

The one or more processors are configured to implement variousinstructions. For example, the one or more processors are configured toexecute document management instructions 408 to implement the documentmanagement engine 116. In this way, processor 402 may be aspecial-purpose computer designed to implement the functions disclosedherein. In an embodiment, the document management engine 116 isimplemented using logic units, FPGAs, ASICs, DSPs, or any other suitablehardware. The document management engine 116 is configured to operate asdescribed in FIGS. 1-3 . For example, the document management engine 116may be configured to perform the steps of process 200 and 300 asdescribed in FIGS. 2 and 3 , respectively.

Memory

The memory 118 is a hardware device that is operable to store any of theinformation described above with respect to FIGS. 1-3 along with anyother data, instructions, logic, rules, or code operable to implementthe function(s) described herein when executed by the processor 402. Thememory 118 comprises one or more disks, tape drives, or solid-statedrives, and may be used as an over-flow data storage device, to storeprograms when such programs are selected for execution, and to storeinstructions and data that are read during program execution. The memory118 may be volatile or non-volatile and may comprise a read-only memory(ROM), random-access memory (RAM), ternary content-addressable memory(TCAM), dynamic random-access memory (DRAM), and static random-accessmemory (SRAM).

The memory 118 is operable to store document management instructions408, public encryption keys 112, a digital document repository 120,digital documents 122, data 124, digital signatures 126, and/or anyother data or instructions. The document management instructions 408 maycomprise any suitable set of instructions, logic, rules, or codeoperable to execute the document management engine 116. The publicencryption keys 112, the digital document repository 120, the digitaldocuments 122, the data 124, and the digital signatures 126 areconfigured similar to the public encryption keys 112, the digitaldocument repository 120, the digital documents 122, the data 124, andthe digital signatures 126 described in FIGS. 1-3 , respectively.

Camera

Examples of the camera 406 include, but are not limited to,charge-coupled device (CCD) cameras and complementarymetal-oxide-semiconductor (CMOS) cameras. The camera 406 is configuredto capture images of graphical codes, people, text, documents, andobjects within a real environment. The camera 406 is configured tocapture images continuously, at predetermined intervals, or on-demand.For example, the camera 406 is configured to receive a command from auser to capture an image. In another example, the camera 406 isconfigured to continuously capture images to form a video stream ofimages. The camera 406 is operable coupled to document management engine116 and provides images to the document management engine 116 forprocessing, for example, to read a graphical code.

Network Interface

The network interface 404 is a hardware device that is configured toenable wired and/or wireless communications. The network interface 404is configured to communicate data between user devices 106, kiosks 104,databases 108, and other devices, systems, or domains. For example, thenetwork interface 404 may comprise an NFC interface, a Bluetoothinterface, a Zigbee interface, a Z-wave interface, a radio-frequencyidentification (RFID) interface, a WIFI interface, a LAN interface, aWAN interface, a PAN interface, a modem, a switch, or a router. Theprocessor 402 is configured to send and receive data using the networkinterface 404. The network interface 404 may be configured to use anysuitable type of communication protocol as would be appreciated by oneof ordinary skill in the art.

While several embodiments have been provided in the present disclosure,it should be understood that the disclosed systems and methods might beembodied in many other specific forms without departing from the spiritor scope of the present disclosure. The present examples are to beconsidered as illustrative and not restrictive, and the intention is notto be limited to the details given herein. For example, the variouselements or components may be combined or integrated with another systemor certain features may be omitted, or not implemented.

In addition, techniques, systems, subsystems, and methods described andillustrated in the various embodiments as discrete or separate may becombined or integrated with other systems, modules, techniques, ormethods without departing from the scope of the present disclosure.Other items shown or discussed as coupled or directly coupled orcommunicating with each other may be indirectly coupled or communicatingthrough some interface, device, or intermediate component whetherelectrically, mechanically, or otherwise. Other examples of changes,substitutions, and alterations are ascertainable by one skilled in theart and could be made without departing from the spirit and scopedisclosed herein.

To aid the Patent Office, and any readers of any patent issued on thisapplication in interpreting the claims appended hereto, applicants notethat they do not intend any of the appended claims to invoke 35 U.S.C. §112(f) as it exists on the date of filing hereof unless the words “meansfor” or “step for” are explicitly used in the particular claim.

The invention claimed is:
 1. A digital document storing device,comprising: a memory operable to store a digital document repositorycomprising a plurality of digital documents; and a processor operablycoupled to the memory, configured to: obtain a first graphical code,wherein the first graphical code is an encoded graphical representationof a public encryption key for an organization; extract the publicencryption key for the organization from the first graphical code;obtain a second graphical code, wherein the second graphical code is anencoded graphical representation of a digital document comprising dataand a digital signature that was signed using a private encryption keyfor the organization; extract the digital document from the secondgraphical code; validate the second graphical code using the publicencryption key for the organization; determine the second graphical codepasses validation using the public encryption key for the organization;and store the digital document in the digital document repository. 2.The device of claim 1, wherein: the first graphical code is a firstQuick Response (QR) code; and the second graphical code is a second QRcode.
 3. The device of claim 1, wherein validating the second graphicalcode comprises: performing a hashing operation on the data to generate afirst hash; decrypting the digital signature using the public encryptionkey to recover a second hash; comparing the first hash and the secondhash; and determining the second graphical code is valid when then firsthash matches the second hash.
 4. The device of claim 1, wherein theprocessor is further configured to: generate a copy of the digitaldocument; and send the copy of the digital document to a second device.5. The device of claim 1, wherein extracting the digital document fromthe second graphical code comprises converting the second graphical codeinto text.
 6. The device of claim 1, wherein the data identifies one ormore items that are associated with the organization.
 7. The device ofclaim 1, wherein data comprises a warranty for an item that isassociated with the organization.
 8. A digital document storing method,comprising: obtaining a first graphical code, wherein the firstgraphical code is an encoded graphical representation of a publicencryption key for an organization; extracting the public encryption keyfor the organization from the first graphical code; obtaining a secondgraphical code, wherein the second graphical code is an encodedgraphical representation of a digital document comprising data and adigital signature that was signed using a private encryption key for theorganization; extracting the digital document from the second graphicalcode; validating the second graphical code using the public encryptionkey for the organization; determining the second graphical code passesvalidation using the public encryption key for the organization; andstoring the digital document in a digital document repository.
 9. Themethod of claim 8, wherein: the first graphical code is a first QuickResponse (QR) code; and the second graphical code is a second QR code.10. The method of claim 8, wherein validating the second graphical codecomprises: performing a hashing operation on the data to generate afirst hash; decrypting the digital signature using the public encryptionkey to recover a second hash; comparing the first hash and the secondhash; and determining the second graphical code is valid when then firsthash matches the second hash.
 11. The method of claim 8, furthercomprising: generating a copy of the digital document; and sending thecopy of the digital document to a second device.
 12. The method of claim8, wherein extracting the digital document from the second graphicalcode comprises converting the second graphical code into text.
 13. Themethod of claim 8, wherein the data identifies one or more items thatare associated with the organization.
 14. The method of claim 8, whereindata comprises a warranty for an item that is associated with theorganization.
 15. A non-transitory computer-readable medium storinginstructions that when executed by a processor cause the processor to:obtain a first graphical code, wherein the first graphical code is anencoded graphical representation of a public encryption key for anorganization; extract the public encryption key for the organizationfrom the first graphical code; obtain a second graphical code, whereinthe second graphical code is an encoded graphical representation of adigital document comprising data and a digital signature that was signedusing a private encryption key for the organization; extract the digitaldocument from the second graphical code; validate the second graphicalcode using the public encryption key for the organization; determine thesecond graphical code passes validation using the public encryption keyfor the organization; and store the digital document in a digitaldocument repository.
 16. The non-transitory computer-readable medium ofclaim 15, wherein: the first graphical code is a first Quick Response(QR) code; and the second graphical code is a second QR code.
 17. Thenon-transitory computer-readable medium of claim 15, wherein validatingthe second graphical code comprises: performing a hashing operation onthe data to generate a first hash; decrypting the digital signatureusing the public encryption key to recover a second hash; comparing thefirst hash and the second hash; and determining the second graphicalcode is valid when then first hash matches the second hash.
 18. Thenon-transitory computer-readable medium of claim 15, wherein theinstructions further cause the processor to: generate a copy of thedigital document; and send the copy of the digital document to a seconddevice.
 19. The non-transitory computer-readable medium of claim 15,wherein extracting the digital document from the second graphical codecomprises converting the second graphical code into text.
 20. Thenon-transitory computer-readable medium of claim 15, wherein the dataidentifies one or more items that are associated with the organization.